Skip to content

chore(deps): [java] update dependency com.google.guava:guava to v33.3.1-jre #14648

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Oct 25, 2024
Merged

chore(deps): [java] update dependency com.google.guava:guava to v33.3.1-jre #14648

merged 3 commits into from
Oct 25, 2024

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.google.guava:guava 33.3.0-jre -> 33.3.1-jre age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the B-dependencies Pull requests that update a dependency file label Oct 25, 2024
@qodo-merge-pro
Copy link
Contributor

qodo-merge-pro bot commented Oct 25, 2024 •
edited
Loading

CI Failure Feedback 🧐

(Checks updated until commit 0883e3c)

Action: Java / Browser Tests (windows) / Browser Tests (chrome, windows)

Failed stage: Run Bazel [❌]

Failed test name: //java/test/org/openqa/selenium/chrome:ChromeDriverFunctionalTest

Failure summary:

The action failed due to issues with the Maven dependencies configuration:

  • Multiple versions of dependencies were detected, which can lead to unexpected behavior.
  • The maven_install.json file contains an invalid input signature and must be regenerated. This
    typically occurs when Maven artifacts have been changed but not repinned.
  • The build process failed because the ChromeDriverFunctionalTest target depends on a package that
    could not be fetched due to the invalid maven_install.json.
  • No test targets were found because the build did not complete successfully.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Microsoft Windows Server 2022
...

581:  com.google.code.gson:gson has multiple versions 2.11.0, 2.8.9
582:  com.google.guava:guava has multiple versions 33.3.1-jre, 31.1-jre
583:  org.mockito:mockito-core has multiple versions 5.13.0, 4.3.1
584:  Please remove duplicate artifacts from the artifact list so you do not get unexpected artifact versions
585:  �[32mINFO: �[0mRepository rules_jvm_external~~maven~maven instantiated at:
586:  <builtin>: in <toplevel>
587:  Repository rule pinned_coursier_fetch defined at:
588:  D:/_bazel/external/rules_jvm_external~/coursier.bzl:1324:40: in <toplevel>
589:  �[31m�[1mERROR: �[0mAn error occurred during the fetch of repository 'rules_jvm_external~~maven~maven':
590:  Traceback (most recent call last):
591:  File "D:/_bazel/external/rules_jvm_external~/coursier.bzl", line 517, column 21, in _pinned_coursier_fetch_impl
592:  fail("%s_install.json contains an invalid input signature and must be regenerated. " % (user_provided_name) +
593:  Error in fail: maven_install.json contains an invalid input signature and must be regenerated. This typically happens when the maven_install artifacts have been changed but not repinned. PLEASE DO NOT MODIFY THIS FILE DIRECTLY! To generate a new maven_install.json and re-pin the artifacts, please run:
594:  REPIN=1 bazel run @maven//:pin
595:  �[31m�[1mERROR: �[0mno such package '@@rules_jvm_external~~maven~maven//': maven_install.json contains an invalid input signature and must be regenerated. This typically happens when the maven_install artifacts have been changed but not repinned. PLEASE DO NOT MODIFY THIS FILE DIRECTLY! To generate a new maven_install.json and re-pin the artifacts, please run:
596:  REPIN=1 bazel run @maven//:pin
597:  �[31m�[1mERROR: �[0mD:/a/selenium/selenium/java/test/org/openqa/selenium/chrome/BUILD.bazel:5:25: //java/test/org/openqa/selenium/chrome:ChromeDriverFunctionalTest depends on @@rules_jvm_external~~maven~maven//:org_mockito_mockito_core in repository @@rules_jvm_external~~maven~maven which failed to fetch. no such package '@@rules_jvm_external~~maven~maven//': maven_install.json contains an invalid input signature and must be regenerated. This typically happens when the maven_install artifacts have been changed but not repinned. PLEASE DO NOT MODIFY THIS FILE DIRECTLY! To generate a new maven_install.json and re-pin the artifacts, please run:
598:  REPIN=1 bazel run @maven//:pin
599:  �[31m�[1mERROR: �[0mAnalysis of target '//java/test/org/openqa/selenium/chrome:ChromeDriverFunctionalTest' failed; build aborted: Analysis failed
600:  �[32mINFO: �[0mElapsed time: 22.420s, Critical Path: 3.75s
601:  �[32mINFO: �[0m1 process: 1 internal.
602:  �[31m�[1mERROR: �[0mBuild did NOT complete successfully
603:  �[31m�[1mFAILED:�[0m 
604:  �[31m�[1mERROR: �[0mNo test targets were found, yet testing was requested
605:  �[0m
606:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @VietND96 VietND96 changed the title chore(deps): update dependency com.google.guava:guava to v33.3.1-jre chore(deps): [java] update dependency com.google.guava:guava to v33.3.1-jre Oct 25, 2024
    @renovate renovate bot changed the title chore(deps): [java] update dependency com.google.guava:guava to v33.3.1-jre chore(deps): update dependency com.google.guava:guava to v33.3.1-jre Oct 25, 2024
    @VietND96 VietND96 changed the title chore(deps): update dependency com.google.guava:guava to v33.3.1-jre chore(deps): [java] update dependency com.google.guava:guava to v33.3.1-jre Oct 25, 2024
    @renovate
    Copy link
    Contributor Author

    renovate bot commented Oct 25, 2024

    Edited/Blocked Notification

    Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

    You can manually request rebase by checking the rebase/retry box above.

    ⚠️ Warning: custom changes will be lost.

    @VietND96
    Format checks
    fd34f36 
    Signed-off-by: Viet Nguyen Duc <[email protected]>
    @VietND96 VietND96 force-pushed the renovate/guava-monorepo branch from a81bfb6 to fd34f36 Compare October 25, 2024 12:48
    @VietND96 VietND96 merged commit c5fbdd6 into trunk Oct 25, 2024
    11 checks passed
    @VietND96 VietND96 deleted the renovate/guava-monorepo branch October 25, 2024 13:53
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Reviewers

    No reviews

    Assignees

    No one assigned

    Labels

    B-dependencies Pull requests that update a dependency file

    Projects

    None yet

    Milestone

    No milestone

    Development

    Successfully merging this pull request may close these issues.

    2 participants

    @VietND96